dyntest.pgc not working in 7.4 ?
От | Seum-Lim Gan |
---|---|
Тема | dyntest.pgc not working in 7.4 ? |
Дата | |
Msg-id | p05100365bbfd280090a5@[192.168.10.94] обсуждение исходный текст |
Ответы |
Re: dyntest.pgc not working in 7.4 ?
|
Список | pgsql-bugs |
Hi everyone, We compiled the dyntest.pgc (in src/interfaces/ecpg/test) and tried it out but it seems like it is not able to stop after reading the last record and keep going on forever. sqlcode return is always 0 and never get to 100 where it is supposed to. The dyntest.pgc has not changed from 7.3.4 to 7.4 and it used to work in 7.3.4. This is PostgreSQL 7.4 in Sparc Solaris 9. Any idea ? Gan $ psql Welcome to psql 7.4, the PostgreSQL interactive terminal. Type: \copyright for distribution terms \h for help with SQL commands \? for help on internal slash commands \g or terminate with semicolon to execute query \q to quit Field separator is " ". A=> select * from lucytest; c1 ---------- record 1 record 2 (2 rows) A=> \q $ $ ./lucyDyntest74 lucytest sqlcode=0 1 Columns c1 varchar(100) 'record 1'| sqlcode=0 'record 2'| sqlcode=0 'record 2'| sqlcode=0 'record 2'| sqlcode=0 'record 2'| sqlcode=0 'record 2'| sqlcode=0 'record 2'| sqlcode=0 'record 2'| sqlcode=0 'record 2'| sqlcode=0 'record 2'| sqlcode=0 'record 2'| sqlcode=0 .... .... $ $ $ ldd lucyDyntest74 libecpg.so.4 => /platdb/lib/libecpg.so.4 libc.so.1 => /usr/lib/libc.so.1 libpgtypes.so.1 => /platdb/lib/libpgtypes.so.1 libpq.so.3 => /platdb/lib/libpq.so.3 libm.so.1 => /usr/lib/libm.so.1 libdl.so.1 => /usr/lib/libdl.so.1 libresolv.so.2 => /usr/lib/libresolv.so.2 libsocket.so.1 => /usr/lib/libsocket.so.1 libnsl.so.1 => /usr/lib/libnsl.so.1 libmp.so.2 => /usr/lib/libmp.so.2 /usr/platform/SUNW,Ultra-80/lib/libc_psr.so.1 $ -- +--------------------------------------------------------+ | Seum-Lim GAN email : slgan@lucent.com | | Lucent Technologies | | 2000 N. Naperville Road, 6B-403F tel : (630)-713-6665 | | Naperville, IL 60566, USA. fax : (630)-713-7272 | | web : http://inuweb.ih.lucent.com/~slgan | +--------------------------------------------------------+
В списке pgsql-bugs по дате отправления: